﻿<%@ Page Language="C#" MasterPageFile="~/Views/Shared/Site.Master" Inherits="System.Web.Mvc.ViewPage" %>

<asp:Content ID="aboutTitle" ContentPlaceHolderID="TitleContent" runat="server">
    About Us
</asp:Content>

<asp:Content ID="aboutContent" ContentPlaceHolderID="MainContent" runat="server">
    <h2>About</h2>
    <p>
        <h3>What Managed Services Framework wants to achieve ?</h3>
        <br />
        There are four things that Managed Services Framework wants to achieve. <br />
        <ul>
            <li>Container for Sub Services, so that it can host service lets</li>
            <li>Provide a Scheduler on Managed Code</li>
            <li>Allow to deploy workflows composed of subservices</li>
            <li>And finally enable integration</li>
        </ul>
        <h4>Container for Sub Services, so that it can host service lets</h4>        
        <p> All these days we have been working with Windows Services. Essentially, the .NET Framework provides very good support for creating Windows Service. The Service Control Manager provides a great UI for managing the Services, Start them, Stop them and Restart them Pause Them and Continue them.
            <br />
                The idea of Managed Services Framework, is to achieve the same apart from some other important features:
            <ul>
                <li> Lightweight Alternative to Windows Services</li>
                <li> Auto Replication of Managed Service Instances</li>
                <li> Easy Deployment</li>
                <li> Configurable Delayed Start</li>
                <li> Live Performance(with/without) Monitors</li>
                <li> Hot Configuration Changes</li>
                <li> Scheduled Restarts</li>
                <li> Conditional Restarts</li>
                <li> Web Monitoring</li>
            </ul>
         </p>
         <h4>Provide a Scheduler on Managed Code through sub services</h4>
         <p>
            Have you ever wanted to write a scheduled job that runs on 15 day of the year and does something. 
            And what about a scenario where in, you want your Scheduled Job A to finish and then if it has finished successfully Schedule Job B starts.
         </p>
         <h4>Allow to deploy workflows composed of subservices</h4>
         <p>
            It does not stop, at Scheduler workflows. It will try to strive for providing a lightweight 
            framework for creating and deploying workflows and get you some business value.
         </p>
         <h4>And finally enable integration</h4>
         <p>
            And finally the ultimate goal is to evolve as a good intergation solution. 
            That's the dream sanket has been chasing and is striving hard to achieve it
         </p>
         <h4>About Sanket</h4>
         <p>
            He is the most unsocial element you can come across the whole world, but he dreams of integrating applications, how sarcastic.
            And he retorts, "Being unsocial gives me the justification of why others should not suffer, what I always :)"
            <br />
            Enough of the blabber,<br />
            Mail Stop: <a href="mailto:naik_sanket@hotmail.com">naik_sanket@hotmail.com</a><br />
            LinkedIN: <a href="http://in.linkedin.com/in/sanketn">http://in.linkedin.com/in/sanketn</a> 
         </p>
    </p>
</asp:Content>
